Methods and systems for administrating imaging device event notification

ABSTRACT

Aspects of the present invention relate to systems, methods and devices for imaging device event notification administration and subscription. Some aspects relate to selective imaging device event notification based on user credentials and/or the occurrence of a specific event. Some aspects relate to the construction, maintenance and use of an event subscription record that is used to manage imaging device event notification.

RELATED REFERENCES

This application is a continuation-in-part of U.S. patent applicationSer. No. 10/962,248, entitled “Methods and Systems for Imaging DeviceRemote Application Interaction,” filed on Oct. 8, 2004; this applicationis also a continuation-in-part of U.S. patent application Ser. No.10/961,793, entitled “Methods and Systems for Imaging Device Remote FormManagement,” filed on Oct. 8, 2004; this application is also acontinuation-in-part of U.S. patent application Ser. No. 10/961,911,entitled “Methods and Systems for Imaging Device Remote LocationFunctions,” filed on Oct. 8, 2004; this application is also acontinuation-in-part of U.S. patent application Ser. No. 10/961,594,entitled “Methods and Systems for Imaging Device Remote documentManagement,” filed on Oct. 8, 2004; and this application is also acontinuation-in-part of U.S. patent application Ser. No. 10/962,103,entitled “Methods and Systems for Imaging Device Document Translation,”filed on Oct. 8, 2004; this application also claims the benefit of U.S.Provisional Patent Application No. 60/704,066, entitled “Methods andSystems for Imaging Device Applications,” filed Jul. 28, 2005.

FIELD OF THE INVENTION

Embodiments of the present invention comprise methods and systems forimaging device event notification.

BACKGROUND OF THE INVENTION

Imaging devices such as printers, copiers, scanners and fax machines canhave a wide array of functions and capabilities to fit specific uses orcombinations of uses. Imaging devices often take the form of amulti-function peripheral device (MFP) that combines the functions oftwo or more of the traditionally separated imaging devices. An MFP maycombine any number of imaging devices, but typically comprises thefunctions of a printer, scanner, copier and fax machine.

Some imaging devices may contain computing resources for data storageand processing such as processors, hard disk drives, memory and otherdevices. As imaging devices add more features and functions, they becomemore costly and complex.

More complex imaging devices and MFPs may comprise network connectivityto provide communication with other computing devices, such as personalcomputers, other imaging devices, network servers and other apparatus.This connectivity allows the imaging device to utilize off-boardresources that are available on a connected network.

Imaging devices typically have a user input panel with an array ofbuttons, knobs and other user input devices. Some devices also have adisplay panel, which can be for display only or can be a touch paneldisplay that enables user input directly on the display.

Devices with touch panel displays or displays with buttons arranged incooperation with the display can display menu data that may be selectedby user input. This menu data is typically driven by an on-board servermodule within the imaging device.

BRIEF SUMMARY OF THE INVENTION

Embodiments of the present invention comprise systems, methods anddevices for interacting with a remote computing device from an imagingdevice. These embodiments comprise remote computing devices configuredto communicate with imaging devices, imaging devices configured tocommunicate with remote computing devices and systems comprising variouscombinations of remote computing devices in communication with imagingdevices.

Embodiments of the present invention comprise methods and systems forimaging device event notification.

The foregoing and other objectives, features, and advantages of theinvention will be more readily understood upon consideration of thefollowing detailed description of the invention taken in conjunctionwith the accompanying drawings.

BRIEF DESCRIPTION OF THE SEVERAL DRAWINGS

FIG. 1 is a diagram of an embodiment of the present invention comprisingan imaging device in connection with a remote computing device;

FIG. 2 is an image of an exemplary user interface for an imaging device;

FIG. 3 shows an exemplary imaging device;

FIG. 4 is a chart depicting steps of an imaging device method;

FIG. 5 is a chart depicting steps of an imaging device method using amarkup language;

FIG. 6 shows an exemplary remote computing device embodiment;

FIG. 7 is a diagram showing components of an exemplary remote computingdevice;

FIG. 8 is a chart showing steps of a remote computing device method;

FIG. 9 is a chart showing steps of a remote computing device methodusing a markup language;

FIG. 10 is a diagram showing a system comprising multiple imagingdevices in connection with a remote computing device;

FIG. 11 is a chart showing steps of a method comprising RCD processingof user input data;

FIG. 12 is a diagram showing components of some embodiments comprisinglinked resources;

FIG. 13 is a diagram showing a system for imaging device eventnotification;

FIG. 14 is a chart showing steps of an embodiment comprising eventnotification subscription;

FIG. 15A is a chart showing steps of an embodiment comprising eventnotification subscription using event types and Job ID;

FIG. 15B is a chart showing steps of an alternative embodimentcomprising event notification subscription using event types and Job ID;

FIG. 16 is a chart showing steps of an embodiment comprising eventnotification subscription using a delivery mechanism;

FIG. 17 is a chart showing steps of an embodiment comprising eventnotification subscription using event types, job ID and a deliverymechanism;

FIG. 18 is a chart showing steps of an embodiment comprising eventnotification access control;

FIG. 19 is a chart showing steps of an embodiment comprising eventnotification access control using a request for credentials;

FIG. 20 is a chart showing steps of an embodiment comprising eventnotification access control using an authentication application;

FIG. 21 is a chart showing steps of an embodiment comprising eventnotification access control using a request for credentials and anauthentication application;

FIG. 22 is a chart showing steps of an embodiment comprising eventnotification access control when requested notification requirescredentials;

FIG. 23 is a chart showing steps of an embodiment comprising eventnotification access control using an authentication application whennotification requires credentials;

FIG. 24 is a chart showing steps of an embodiment comprising eventnotification access control using a credential request when required;

FIG. 25 is a chart showing steps of an embodiment comprising eventnotification access control using an authentication application andcredential request;

FIG. 26 is a chart showing steps of an embodiment comprising eventnotification;

FIG. 27 is a chart showing steps of an embodiment comprising eventnotification with global subscriptions;

FIG. 28 is a chart showing steps of an embodiment comprising eventnotification using a delivery mechanism;

FIG. 29 is a chart showing steps of an embodiment comprising eventnotification using a global subscription and a delivery mechanism;

FIG. 30 is a diagram showing elements of an embodiment comprising a CoreWeb Service Framework; and

FIG. 31 is a diagram showing interaction with a Core Web ServiceFramework.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Embodiments of the present invention will be best understood byreference to the drawings, wherein like parts are designated by likenumerals throughout. The figures listed above are expressly incorporatedas part of this detailed description.

It will be readily understood that the components of the presentinvention, as generally described and illustrated in the figures herein,could be arranged and designed in a wide variety of differentconfigurations. Thus, the following more detailed description of theembodiments of the methods and systems of the present invention is notintended to limit the scope of the invention but it is merelyrepresentative of the presently preferred embodiments of the invention.

Elements of embodiments of the present invention may be embodied inhardware, firmware and/or software. While exemplary embodiments revealedherein may only describe one of these forms, it is to be understood thatone skilled in the art would be able to effectuate these elements in anyof these forms while resting within the scope of the present invention.

Embodiments of the present invention comprise interfaces andarchitecture that integrate imaging devices with remote computing deviceapplications and environments to provide solutions that may not bepossible solely with an imaging device alone. Some embodiments comprisean infrastructure and set of interfaces that allow applications on anetwork to programmatically control imaging device functions andinteract with a user through an imaging device input panel. Softwarefunctions that are not practical within the imaging device can beperformed on the server but are accessible from the imaging device.

For the purposes of this specification and claims, an imaging device(IDev) may be described as a device that performs an imaging function.Imaging functions comprise scanning, printing, copying, imagetransmission (sending and receiving), image conversion and otherfunctions. Exemplary imaging devices comprise printers, copiers,facsimile machines, scanners, computing devices that transmit, convertor process images and other devices. An IDev may also perform multipleimaging functions. For example, and not by way of limitation, amulti-function peripheral device (MFP), which typically has thecapability to perform a plurality of functions comprising a printer,scanner, copier and/or a facsimile machine or imagetransmitter/receiver, is a type of imaging device. Other MFP imagingdevices may comprise other combinations of functions and still qualifyas an IDev.

For the purposes of this specification and claims, a remote computingdevice (RCD) is a device capable of processing data and communicatingwith other devices through a communications link. An RCD is a remotedevice because it requires a communications link, such as a networkconnection, a telephone line, a serial cable or some other wired orwireless link to communicate with other devices such as an imagingdevice. Some exemplary RCDs are network servers, networked computers andother processing and storage devices that have communications links.

Some embodiments of the present invention may be described withreference to FIGS. 1 & 2. These embodiments comprise an imaging device(IDev) 4 that may be a multi-function peripheral device (MFP) or asingle function device. The imaging device 4 further comprises a userinterface (UI) panel 2, which may comprise input buttons 14 and adisplay device 12 or may comprise a touch panel system with or withoutbuttons 14. User input and display may also be performed through aseparate UI device 8, which may be connected to the imaging device 4 bya communication link 12, such as a USB connection, a network cable, awireless connection or some other communications link. UI device 8 maycomprise an input device, such as a keyboard or buttons as well as adisplay device, which may also be a touch screen panel. UI device 8 mayalso comprise an interface for transfer of instructions that are inputto the device 8 from a remote input device. This form of UI device 8 maycomprise memory sticks, USB memory cards and other storage devices thatmay be configured to store input for transfer to an imaging device.

These embodiments further comprise a remote computing device (RCD) 6that is linked to the imaging device 4 via a communications link 10,such as a network connection. This network connection may be a typicalwired connection or a wireless link.

Embodiments of the present invention may provide menu data from the RCD6 to the imaging device UI panel 2 or remote panel 8 via the networkconnection 10. Once this menu data is fed to the imaging device 4, an UIpanel 2, 8 on the imaging device 4 may be used to interact withapplications that run on the remote computing device 6. User inputreceived from UI panels 2, 8 may be returned directly to the remotecomputing device 6.

A Web Service is a software application identified by a Uniform ResourceIdentifier (URI), whose interfaces and binding are capable of beingdefined, described and discovered by Extensible Markup Language (XML)artifacts and supports direct interactions with other softwareapplications using XML based messages via Internet-based protocols.

An application on the remote computing device 6 may use one or more WebServices to control various features in the imaging device 4, such asenabling, disabling or setting device values or controlling devicefunctions.

Embodiments of the present invention allow network applications runningon remote computing devices to interact with the user of the imagingdevice through the imaging device I/O panel. These embodiments allowimaging device user interface (UI) control (i.e., touch panel,button/display) by applications. Some embodiments may also integratecustom display screens or menus with the native imaging device UI.Embodiments may hand off control of imaging device functions betweenstandard operation modes performed on the imaging device in response touser input to an imaging device UI and open systems modes that utilizenetwork resources, such as applications on RCDs, through user input atthe imaging device UI.

Embodiments of the present invention comprise network-based applicationsthat have full control over the imaging device UI to display text andgraphics in any format. In these embodiments, the application canprogrammatically display buttons, textboxes, graphics, etc. in anylayout desired.

In some embodiments, the UI layout is easy to program using a standardlanguage, such as a markup language. These languages comprise HypertextMarkup Language (HTML), Extensible Markup Language (XML), WirelessMarkup Language (WML), Extensible Hypertext Markup Language (XHTML) andother languages.

In some embodiments of the present invention a remote computing deviceapplication or server application is able to request a keyboard UI to bedisplayed on the imaging device display 12, 8. In some embodiments, thisfunctionality is available on the imaging device and does not need to berecreated by remote computing device applications. In some embodiments,the remote computing device may define the keyboard prompt and defaultvalues. These embodiments may comprise a remote computing device that isable to rename imaging device UI buttons, such as the OK and Cancelbuttons as well as define additional buttons.

In some embodiments, menu templates may be served to the imaging deviceUI by the imaging device itself 4 or from a remote computing device 6.

External Authorization Application

Some embodiments of the present invention may comprise a remotecomputing device application that is registered as the ExternalAuthorization server. The External Authorization application may controlaccess to the imaging device and may have top-level control of the UI.UI control may be given to this application in the same manner thatcontrol is given to an internal auditor.

In these embodiments, when an imaging device system boots, it checks tosee if an External Authorization application is registered. If so, theimaging device is placed in disabled mode and the application iscontacted to take control of the UI. If the External Authorizationserver is not available, an error message may be displayed and thedevice may remain disabled. The imaging device may periodically try tocontact the External Authorization server until it is available. Table 1below describes what entity has control of the UI, in an exemplaryembodiment, when the device is in a disabled state.

TABLE 1 UI Control in Disabled State Button Press UI Control IndicatorLights Device boots External Application None Document Filing ExternalApplication None Image Send External Application None Copy ExternalApplication None Job Status Device - standard Job Status Job Statusscreens Custom Settings Device - standard Custom Settings N/A screens OSMode Not available when device is disabledRemote Computing Device Applications

In embodiments of the present invention, access to the custom UI panelsof imaging devices may vary from application to application. Somesolutions, such as Document Management integration, may wish to leveragethe native Image Send screens, but display some custom UI's to gatheradditional information about a scan job. Other solutions, like customprinting applications, may be accessed from a separate mode than thenative functions.

In order to accommodate the diversified needs of these solutionsapplications, embodiments may support multiple integration points for UIcontrol. These integration points are based on a user action (“trigger”)for which applications may register. In some embodiments, applicationsmay be registered with target devices so that the device knows that when“trigger A” occurs on the front panel to contact “remote computingdevice B” for instructions. In exemplary embodiments, applications maybe integrated with an imaging device at any of several “trigger” points.

Remote computing devices may be registered to a specific function andcontacted when that function's hardware key is pressed (e.g. Image Send)on the imaging device UI. Any UI information provided by the remotecomputing device may be displayed instead of the standard functionscreens native to the imaging device. This trigger may be used forapplications that wish to replace the existing functions with completelycustom UI's, such as an alternative scan solution or a specializeddisplay, such as a “Section 508” compatible screen or otherspecialized-need interface that may have large buttons or otheraccommodations.

In some embodiments, each function on the imaging device may have a menuon the touch screen that remote computing devices, such as servers, canregister. This enables solutions applications to provide custom contentand still use some of the standard functionality provided by the imagingdevice. When a button assigned to a custom application is selected, amenu will be displayed with the solutions registered to that function.Users may select the desired solution and the remote computing devicewill be contacted for instructions.

In some embodiments, a stand-alone RCD mode that provides remotecomputing device application access can be accessed from the job queueportion of the UI that is displayed on every screen. This trigger pointmay be used for applications that do not fit within one of the standarddevice functions, such as custom printing solutions on an imagingdevice. When the RCD menu is selected, a menu will be displayed with thesolutions applications registered to the generic RCD mode. Users willselect the desired solution and the remote computing device will becontacted for instructions.

Hardware Key Interaction

In some embodiments of the present invention, when an imaging device isenabled, additional hardware keys may be used to manage the device.Hardware key assignments for an exemplary embodiment are shown in table2.

TABLE 2 Exemplary Hardware Key Assignments Standard Button Press IDevMode RCD Mode Mode keys (Copy, Clear current job Clear current jobsettings, Doc Filing, Image settings, move move to target screen Send)and Custom to target screen Settings key Job Status key Move to JobStatus, Move to Job Status, maintain current maintain current settings &settings & UI UI location location Clear (C) Clears settings Sends clearevent to external application Clear All (CA) Clears settings, Cancelsjob and returns to cancels job, and default IDev screen returns todefault (notification sent to external IDev screen application) **WhenExternal Authorization is controlling the UI, only notification is sentStart Initiates scan Initiates scan function function Number keys Inputfor copy count Not used or fax numbers * Logs user out Logs user out(disable (disable device and device and contact External contactExternal Authorization for screens) Authorization for screens)

In some embodiments, in addition to the * key for logout, a timeoutperiod may be implemented. Some embodiments also comprise an auto clearsetting that can be configured for a given period of time, such as 10 to240 seconds (or disabled). In these embodiments, when there is noactivity for the time configured in auto clear, the device mayautomatically return to disabled mode and attempt to contact a remotecomputing device to retake control of the UI.

Error & Jam Notifications

Depending on a particular solution, a remote computing deviceapplication may have full or only partial control of the imaging deviceUI and a particular imaging job. In some embodiments, partial controlmay include cases where a remote computing device is monitoring clicks,but native modes are responsible for the UI interaction and controllingthe job. Partial control may also include cases where the remotecomputing device application is integrated with a native mode (UItrigger=function custom menu). In these embodiments, the imaging devicemay handle all error and jam notifications with only a notification sentto the relevant remote computing device application.

For some embodiments, in cases where the remote computing deviceapplication has full control over the UI and the job, error and jamnotifications may be handled differently depending on the type of error.For recoverable errors, a notification may be sent to the remotecomputing device application and the application may be responsible fordisplaying messages and resolving the error. For non-recoverable errors,the imaging device and RCD mode may interact to gracefully handle theerror condition (e.g. provide user with instructions for clearing jam).

Control Handoffs

In some embodiments, at different points throughout an imaging job,several applications may need control over an imaging device including,but not limited to, an External Authorization application, a standardRCD application, an imaging device native mode and other applications.The following section describes, for an exemplary embodiment, thevarious steps in an exemplary job, the entities that may have controlduring each step, and what type of control may be allowed.

Step 1: User provides credentials to access the device at the device UI.This step may be controlled by a remote computing device, such as anExternal Authorization application or by Internal Accounting (nativemode) in the imaging device itself. At the end of this step, the deviceis enabled. The External Authorization application may also specifydefault parameters or disable specific job parameters (e.g. default fileformat is PDF, but user may change; color mode is set to B/W and usermay not change).

Step 2: User sets parameters for the job using one of the native imagingdevice modes or a standard RCD application. At the end of this step theuser makes an input to initiate the job. When the input is made, anoptional notification may be sent to the standard RCD application, whichcan then change job parameters if desired. An e-mail application is oneexample of an application that may request notification when the userinput is made. A user may use native Image Send screens or other inputto select scan options and choose e-mail recipients. A user may thenselect a custom application button and choose the scan-to-e-mail optionfrom the menu. The e-mail application may then display custom screensfor the user to set permissions for the file. Once a user places theoriginal document(s) on the scanner and initiates the process, thee-mail application may capture the destination parameters set by theuser and change the target destination to the e-mail application FTPserver. The e-mail application may then receive the file, apply theappropriate permissions, and send to the e-mail recipients selected bythe user. A remote computing device application may also want to retakecontrol of the UI at this point, if, as in some embodiments, theapplication generates thumbnails of the scanned images and displays themto the user for verification.

Step 3: Once the job is initiated, the imaging device is responsible forscanning or RIPing the job and spooling it to the HDD. If the imagingdevice is configured to authorize jobs with an external authorizationapplication, it may send a click report to the application and wait forinstructions. The external authorization application may enable the jobfor sending/printing, cancel the job, or change job parameters (and thenenable). As an example, a rules-based printing application may wish tochange job parameters after it receives a click report. Some rules-basedprinting applications support rules-based printing and scanning that canlimit what each user is allowed to do based on the time of day, thedestination, or many other parameters. For example, only users in themarketing group may be able to scan high-quality color images. If a userfrom another group selects color and 600 dpi, a rules-based applicationmay change the parameters to color and 200 dpi. At the end of this stepthe job should either be authorized or canceled.

Step 4: In some embodiments, this may be an optional step, where thestandard RCD application in step 2 may have specified the destination asa HDD for temporary storage. This step may also be used, in someembodiments, by a Java application running on the imaging device. Forexample, a government office may have a custom encryption applicationrunning on the device that takes the scanned document, encrypts it, andthen requests the imaging device to send it to the target destinationselected by the user in step 2. In some embodiments, it may bebeneficial to send a notification to the external authorizationapplication after this step—because the imaging device does not know howlong the file will be on the HDD or what the application is going to dowith it—and after the send/print step.

Step 5: In the final step, the file is actually output. In typicalembodiments, the file is either sent over the network or printedlocally. At the end of this step, a notification that the job wassuccessfully completed should be sent to the external authorizationapplication and optionally, to the standard RCD application.

Device Control and Management API's

The API's may be used to allow a remote computing device application tocontrol access to an imaging device for vend applications and to managethe device from a remote location.

Device Control and Vend API

In some embodiments of the present invention, a Device Control and VendAPI allows applications to enable and disable access to the device andtrack click counts. The Device Control and Vend API may provide an RCDwith the following controls:

Enable/disable device of function—this may allow an RCD to enable ordisable access to the device as a whole or by function to enforceindividual user privileges. In some exemplary embodiments, the functionslisted in Table 3 may be selectively enabled or disabled by anapplication.

TABLE 3 Device Functions Enable/Disable Description Copy Copy function(Copy button) Image Send Scan and fax function, plus send from DocFiling (Image Send button) Document Filing All access to Document Filingfunctions (Document Filing button) Print Network prints, pull print fromfront panel, and print from Document Filing (No button control)

Report clicks used—at the end of a successful job, the clicks used maybe reported back to an RCD including:

TABLE 4 Job and Page Characteristics Fax PC- E-mail/ Broad- Scan ItemCopy Print Send Fax FTP cast to HD JOB Characteristics Job Mode Yes YesYes Yes Yes Yes Yes Broadcast No No Yes Yes Yes Yes No Manage No. UserName Yes Yes Yes Yes Yes Yes Yes Address No No Yes Yes Yes # No StartTime Yes Yes Yes Yes Yes Yes Yes End Time Yes Yes Yes Yes Yes Yes YesTotal Page Yes Yes Yes Yes Yes Yes Yes Result Yes Yes Yes Yes Yes YesYes Error Cause No No Yes Yes Yes Yes No Doc Filing Yes Yes Yes Yes YesYes Yes Save Mode *1 *1 *1 *1 *1 *1 *1 File Name *1 Yes *1 Yes Yes *1Yes File Size Yes Yes *1 *1 *1 *1 Yes Resolution Yes Yes Yes Yes Yes YesYes Special Yes Yes Yes No Yes Yes Yes Finishing Yes Yes No No No No NoFile Format No No No No Yes Yes No Compression No No No No Yes Yes NoPAGE Characteristics Copy Yes Yes Yes Yes Yes # Yes Paper Size Yes YesYes Yes Yes Yes Yes Simplex/duplex Yes Yes Yes Yes Yes Yes Yes PaperType Yes Yes Yes Yes No No Yes Page Yes Yes Yes Yes Yes Yes Yes *1 - Yeswhen Document Filing is used

Debit mode—in these embodiments, when an application enables the deviceit may specify if the current job requires authorization. If so, the jobwill be spooled to memory and click information (e.g., as defined inTable 4) will be sent to an RCD. An RCD will then notify the device ifthe job should be deleted or output/sent. At this point, the applicationalso has the option of changing job parameters. If the application doesnot require authorization, the job will continue as normal and a clickreport will be sent at the end of the job.

Print job accounting—in these embodiments, an RCD may wish to monitorprint jobs along with walk-up functions. For print job accounting, anIDev may monitor all incoming print jobs and send accounting data in thePJL header to an RCD for verification before printing the job. The RCDwill evaluate the accounting data (or lack thereof) and inform the IDevto continue with or cancel the job.

Report on unidentified jobs—in these embodiments, an RCD may also wishto monitor print jobs that it cannot associate to a specific user, suchas device reports and incoming fax jobs. The RCD can register to receiveclick counts for all unidentified jobs, so that it may bill them to ageneral account.

Device Management API

In some embodiments of the present invention, a Device Management APIallows a network application to remotely setup and manage the imagingdevice. In exemplary embodiments, the Device Management API may providean RCD with the following controls:

-   -   Device status—an RCD may request the current status of the        device. This is the same status information as reported on the        embedded web pages.    -   Device configuration—an RCD can retrieve a list of installed        options supported by the device.    -   Web Page settings—an RCD application can retrieve and set any of        the values that are configurable on the embedded web pages.    -   Key Operator Programs—an RCD application can retrieve and set        any of the values that are configurable in Key Operator        Programs, including software keys.    -   Custom Settings—an RCD application can retrieve and set any of        the values that are configurable in Custom Settings.    -   Job Status—an RCD application can retrieve the current job queue        and history information and reprioritize or delete jobs in the        queue.    -   Click counts—an RCD application can retrieve device total counts        and clicks for each function by account code.    -   Data Security settings—an RCD application may retrieve the        status information on the DSK (e.g. last erase) and initiate        data clear functions.    -   RED data—an RCD can retrieve all data typically sent in a RED        message.    -   Remote reboot—an RCD can initiate a reboot of the imaging        device.

The above groupings are provided only as an exemplary embodimentdetailing which settings should be included. In some embodiments, actualAPI's should be grouped by functional areas since there may be overlapbetween Key Operator settings and web page settings.

Internal Accounting API

In some embodiments, an Internal Accounting API may allow a remotecomputing device application to configure internal accounting and reportclick counts. In some exemplary embodiments an Internal Accounting APImay include:

-   -   Set Auditing Options—an RCD may set auditing options including        which modes auditing is enabled for, “account number security”,        and “cancel jobs of invalid accounts.”    -   Manage Account Codes—an RCD can add, edit, or delete account        codes    -   Account Limits—an RCD application can specify a maximum number        of clicks by function for individual account codes or for all        account codes    -   Account Reset—an RCD application can reset the click count for        an individual account or for all accounts    -   Retrieve Clicks—an RCD can retrieve the number of clicks by        function for each account code        Font and Form Management API

Some embodiments of the present invention may comprise a Font and FormManagement API, which allows an RCD application to remotely download andmanage fonts and forms in mass-storage. In some exemplary embodiments, aFont and Form Management API may provide a remote computing device withthe following controls:

-   -   Mass storage control—an RCD application can retrieve mass        storage status information including storage capacity, space        available, and write-protect mode plus modify write-protect        status.    -   Resource list—an RCD application can retrieve a list of stored        fonts and forms including font or macro ID, font number,        font/form name, escape sequence, and file size.    -   Download resource—an RCD application can download PCL fonts, PCL        macros, and PS fonts and forms. Any special processing that is        performed when a resource is downloaded via the web pages will        also be performed when the resource is downloaded via Open        Systems.    -   Delete resource—an RCD application can delete any resource        stored in mass storage.    -   Upload resources—an RCD application can upload an individual or        all resources. On devices where effective memory management is        unavailable, a server application can use this function to        “defrag” mass storage.    -   Font/macro ID's—an RCD application can assign or modify the ID's        assigned to PCL fonts and macros.        Firmware Management API

In some embodiments of the present invention, a Firmware Management APImay allow a remote computing device or network application to remotelydownload and manage the imaging device firmware. In some exemplaryembodiments, a Firmware Management API may provide a remote computingdevice (e.g., a server) with the following controls:

-   -   Firmware versions—an RCD application can retrieve the current        firmware version numbers.    -   Service mode—an RCD application can place the MFP in service        mode to lockout other jobs that will interfere with firmware        upgrade. Upon receiving a service mode request, the IDev will        stop accepting incoming jobs, complete all jobs in the queue,        and then notify the server that it is in service mode.    -   Update firmware—an RCD can download an updated firmware version        to the device. If a reboot is necessary, the IDev will perform        it automatically when download is complete.    -   Download status—the IDev will send a status notification        (success/error) to an RCD after firmware download.    -   Revert to previous version—if firmware update is not successful,        the application can request the IDev to revert to the previous        firmware version.

Device Function API's

In some embodiments of the present invention, device function API'sallow a remote computing device application to use existing imagingdevice functionality to provide new custom solutions.

Image Send API

In some embodiments, an Image Send API may provide the remote computingdevice application with the following controls:

-   -   Image Send Parameters—a remote computing device application can        get and set values for the following scan and fax parameters:        -   COLOR OR B/W        -   IMAGE MODE—TEXT, TEXT/PHOTO, PHOTO; EXPOSURE LEVEL        -   RESOLUTION        -   FILE FORMAT—FILE TYPE, COMPRESSION, AND PAGES PER FILE        -   ORIGINAL—ORIGINAL SIZE, SIMPLEX/DUPLEX, ROTATE, AND JOB            BUILD        -   FILENAME        -   SUBJECT        -   MESSAGE        -   SENDER        -   SCHEDULE SEND TIME        -   PAGE DIVISION (BOOK SCANNING)        -   COVER PAGE        -   TRANSMISSION MESSAGE (CONFIDENTIAL, URGENT, ETC.)        -   THIN PAPER SCANNING        -   DESTINATION        -   DOCUMENT FILING    -   Initiate Scan—the remote computing device application can        initiate the scan function (same as user pressing start button).

In some embodiments, a remote computing device can change the defaultvalues on the imaging device or the values for the current job. For thecurrent job, the remote computing device may also specify if scanparameters may be modified by the user or not. If one remote computingdevice application (e.g. Access Control) specifies that a parametercannot be changed and then a second application (e.g. DocumentManagement) tries to set the parameter, a notification may be sent tothe second application and the setting will not be changed.

Print API

In some embodiments, print jobs may be submitted by remote computingdevice applications using standard printing channels. In some exemplaryembodiments, a Print API may provide a remote computing device with thefollowing additional control:

-   -   PJL sniffing—an RCD application can register with the IDev to be        contacted for instructions when a specific PJL command is found        in a print job. The RCD can then instruct the IDev to replace        the command, cancel the job, or continue printing. This        interface may be used in applications like accounting and        other-brand compatibility.        Copy API

In some embodiments of the present invention, a Copy API may provide aremote computing device with the following exemplary controls:

-   -   Copy Parameters—an RCD application can get and set values for        the following copy parameters:        -   COLOR OR B/W        -   EXPOSURE—TEXT, TEXT/PHOTO, PHOTO, SUPER PHOTO; EXPOSURE            LEVEL        -   PAPER SELECT (BY TRAY)        -   COPY RATIO        -   2-SIDED COPY—1TO1, 1TO2, 2TO2, 2TO1; BINDING EDGE        -   OUTPUT—OUTPUT TRAY, SORT, STAPLE, GROUP, OFFSET        -   ORIGINAL SIZE        -   SPECIAL FUNCTIONS—MARGIN SHIFT, ERASE, PAMPHLET, ETC.        -   DOCUMENT FILING    -   Initiate Copy—an RCD application can initiate the copy function        (same as user pressing start button).

In some embodiments, a remote computing device can change the defaultvalues on the imaging device or the values for the current job. For thecurrent job, the remote computing device may also specify if copyparameters may be modified by the user or not.

Document Filing API

In some embodiments of the present invention, a Document Filing API mayprovide a remote computing device with the following exemplary controls:

-   -   Backup/restore—the remote computing device application can        import and export a batch file with all Document Filing data. In        some embodiments, this package will be in a proprietary format        since it contains documents that are password-protected and        should not be accessed individually—this is typically for        restore in case of failure or cloning to other devices.    -   File/folder list—the remote computing device application can        retrieve, modify, and create new files and folders to be stored        on the IDev (also covered in device management).    -   Download file—the remote computing device can download a new        file to the Document Filing systems and specify folder,        filename, username, and password.    -   User list—the remote computing device application can retrieve,        modify, and create new users to be stored on the IDev (also        covered in device management).    -   HDD Status—the remote computing device application can retrieve        the current HDD status including the % allocated to the main        folder, quick folder, and custom folders and the % remaining.    -   Doc Filing Parameters—the remote computing device application        can get and set values for storing a file to Doc Filing        including:        -   EXPOSURE        -   RESOLUTION        -   ORIGINAL—SIZE, SIMPLEX/DUPLEX        -   FILE INFORMATION—USERNAME, FILENAME, FOLDER, CONFIDENTIAL,            PASSWORD        -   SPECIAL MODES—ERASE, DUAL PAGE COPY, 2IN1, JOB BUILD, CARD            SHOT    -   Initiate Print—the remote computing device application can        select a stored file and initiate a print including the        following parameters:        -   PAPER SIZE/SOURCE        -   OUTPUT—SORT/GROUP, OUTPUT TRAY, STAPLE, PUNCH, OFFSET        -   SIMPLEX/DUPLEX (TABLET/BOOKLET)        -   TANDEM PRINT        -   NUMBER OF COPIES        -   DELETE OR STORE AFTER PRINTING    -   Initiate Send—the remote computing device application can select        a stored file and initiate a send including the following        parameters:        -   RESOLUTION        -   FILE FORMAT        -   DESTINATION        -   TIMER        -   SENDER        -   FILENAME        -   SUBJECT        -   MESSAGE

Security

Allowing external applications to control an imaging device opens up theimaging device to new security vulnerabilities. In embodiments of thepresent invention that provide some security measures, the followingexemplary items are security concerns that may be addressed by theremote computing device interface.

Access to remote computing device interfaces may be limited to validapplications. Embodiments provide extensive access and control of theimaging device, which poses a significant security risk. The interfaceof these embodiments may be protected from access by attackers, whilemaintaining ease of setup and use for valid solutions.

Confidential data (user credentials and job data) may be protectedduring network transfer. User credentials and job data may be securedduring network transfer to ensure that it cannot be stolen, an intrudercannot monitor device activity, and a man-in-the-middle attack cannotchange messages. Imaging devices may support Secure Sockets Layer (SSL)and other connections to ensure data is safe while being communicatedbetween the imaging device and remote computing device applications.

Administrators may have the ability to lock-down imaging device access.For users with strict security policies, administrators may have theability to disable access by remote computing devices or limit access tospecific applications. Administrators may have an option to register thelimited applications that they wish to access the imaging deviceinterfaces.

Remote computing device applications may ensure the imaging device isnot being “spoofed.” The remote computing device may be able toauthenticate an imaging device that it is contract with it to ensure anintruder cannot imitate the imaging device to collect networkconfiguration and password information, monitor file/folder structuresof a document management system, or spoof security settings and DSKstatus of the imaging device.

A remote computing device may ensure that the server is not being“spoofed.” The imaging device must be able to authenticate all remotecomputing devices that it is in contact with to ensure that an intruderis not spoofing the remote computing device's IP address. By pretendingto be the remote computing device, an intruder could steal usercredentials, redirect scanned documents, change device settings orfirmware, or bring down the access control system (either to provideaccess to unauthorized users or initiate a denial of service attack forvalid users).

Access control/vend applications may not be compromised when a remotecomputing device is unavailable. When the remote computing device isunavailable, it may not be acceptable to provide open access to thedevice. If the remote computing device is unavailable at startup orbecomes unavailable at anytime (e.g. someone disconnects network cable),the imaging device may immediately be disabled and an error messagedisplayed.

An administrator may be able to adjust a security level based on companyand application requirements. Security requirements can have a largeimpact on the time it takes to develop a remote computing deviceapplication and the resources required to implement the solution. Usersusing some embodiments may range from a small business with one imagingdevice, no IT staff, and a simple scan or print application to a largegovernment office using access control and audit trails to track alldevice activity. The security measures used to protect imaging deviceinterfaces may be adjustable by the administrator to match the targetenvironment.

The imaging device and remote computing device applications may be ableto hand-off user credentials. Users may be prompted to login at multiplepoints throughout a job. For example, an access control application oraccounting application may control total device access, the imagingdevice may have user authentication enabled for Image Send, and adocument management application may require user login before showing afolder list. In many environments, all of these applications will use acommon user database. In some embodiments, it is, therefore, desirablefor the applications to pass user credentials to each other, so thateach one does not have to repeat the authentication process.

Some embodiments of the present invention may be described withreference to FIG. 3. These embodiments comprise an imaging device only,which is configured to interact with a remote computing device, such asa server through a communications link. The imaging device 30 comprisesa user interface 32, which comprises a user input device 34, such as akeypad, one or more buttons, knobs or switches or a touch-screen paneland a display 36, which may comprise user input device 34 in the form ofa touch-screen panel.

Imaging device 30 will typically be capable of performing one or moreimaging functions including, but not limited to, scanning, printing,copying, facsimile transmission (sending and receiving) and others.

These embodiments further comprise a communications link 38, which maybe a wired connection (as shown in FIG. 3) comprising a network cable, aUniversal Serial Bus (USB) cable, a serial cable, a parallel cable, apowerline communication connection such as a HomePlug connection orother wired connections. Alternatively, the communications link 38 maycomprise a wireless connection, such as an IEEE 802.11(b) compliantconnection, a Bluetooth connection, an Infrared Data Association (IrDA)connection or some other wireless connection.

The operation of some imaging device embodiments may be explained withreference to FIG. 4. In these embodiments, menu data is received 40 froma remote computing device (not shown in FIG. 3), which is connected tothe imaging device 30 via the communication link 38 through a wired orwireless connection. This menu data is then displayed 42 on the imagingdevice user interface display 36. This display of remote menu data isintended to prompt a user to make an input on the user interface inputdevice 34.

Imaging devices of these embodiments are further configured to acceptinput from a user in response to a display of remote menu data andcommunicate 44 that user input to a remote computing device. In someembodiments, this user input data will be processed by a remotecomputing device. This may comprise running an application on the remotecomputing device. This processing may also comprise accessing andcommunicating data that is stored on the remote computing device.

The imaging devices of these embodiments are further configured toreceive 46 data resulting from processing the user input data. This maycomprise data generated by an application running on the remotecomputing device in response to the user input. The imaging device mayalso receive data that was stored on a remote computing device, such asa file server, in response to processing the user input.

Once the imaging device 30 has received 46 the processed data, theimaging device 30 may perform 48 a native function in response to thedata or using the data. For example, and not be way of limitation, theimaging device 30 may print a document that was stored on the remotecomputing device and modified on the remote computing device accordingto the user input. As another non-limiting example, the imaging device30 may active or enable functions (i.e., scanning, copying, printing,fax transmission) on the imaging device in response to the receipt 46 ofprocessed data.

Some, more specific, imaging device embodiments may be explained withreference to FIG. 5. In these embodiments, the imaging device 30 isconfigured to receive 50 menu data formatted in a markup language from aremote computing device. The communication link by which the menu datais communicated may be established and maintained using a HypertextTransfer Protocol (HTTP). The markup language may comprise terms fromHypertext Markup Language (HTML), Extensible Markup Language (XML),Wireless Markup Language (WML), Extensible Hypertext Markup Language(XHTML) and/or other languages.

Once the menu data is received 50, it may be displayed 52 on the imagingdevice user interface display 36. As in previously describedembodiments, the menu data is typically intended to prompt user input onimaging device user interface 32. Display 52 of the remotely-stored menudata may be accomplished with a browser application that is native tothe imaging device 30.

In these embodiments, the imaging device 30 is further configured toroute 54 user input received though its user interface 32 to a remotecomputing device. The remote computing device that receives the userinput may then run an application or otherwise process the user inputand return the results of the processing to the imaging device 30.Accordingly, the imaging device 30 is further configured to receive 56processed data from a remote computing device. In some embodiments, theimaging device 30 may perform one or more functions in response to thereceipt 56 of processed data.

Some embodiments of the present invention may be explained withreference to FIG. 6. These embodiments comprise a remote computingdevice (RCD) 60, which has a communications link 64. Communications link64 may be a wired connection (as shown in FIG. 6) comprising a networkcable, a Universal Serial Bus (USB) cable, a serial cable, a parallelcable, a powerline communication connection such as a HomePlugconnection or other wired connections. Alternatively, the communicationslink 64 may comprise a wireless connection, such as an IEEE 802.11(b)compliant connection, a Bluetooth connection, an Infrared connection,such as those defined in the Infrared Data Association (IrDA) standardor some other wireless connection. In some embodiments, RCD 60 mayfurther comprise a data storage device 62, which is typically a harddrive, but may also be an optical drive device, such as an array ofcompact disk drives, flash memory or some other storage device.

Embodiments of RCD 60 may be further described with reference to FIG. 7.In these embodiments, RCD 60 comprises a processor 72 for processingdata and running programs such as operating systems and applications.RCD 60 may further comprise memory 74, which may be in the form ofRandom Access Memory (RAM) and Read Only Memory (ROM). Generally, anyapplications processed by processor 72 will be loaded into memory 74.RCD 60 may further comprise a network interface 78, which allows RCD 60to communicate with other devices, such as an imaging device 30. In someembodiments, RCD 60 may also comprise a user interface 80, but this isnot required in many embodiments. Storage 62 may be used to storeapplications and data that may be accessed by an imaging device 30 ofembodiments of the present invention. Processor 72, memory 74, storage62, network interface 78 and, optionally, user interface 80 aretypically linked by a system bus 76 to enable data transfer between eachcomponent. Communications link 64 may couple the RCD 60 to other devicesvia network interface 78.

In some embodiments, described with reference to FIG. 8, an RCD 60 maycomprise menu data stored on storage device 62 or in memory 74. Thismenu data may be configured for display on an imaging device userinterface 32. Menu data may be stored in many formats andconfigurations. In some embodiments menu data may take the form of termsexpressed with a markup language. The markup language may comprise termsfrom Hypertext Markup Language (HTML), Extensible Markup Language (XML),Wireless Markup Language (WML), Extensible Hypertext Markup Language(XHTML) and/or other languages. In these embodiments, menu data may besent 82 through a communications link 64 to an imaging device 30.Accordingly, menu data configured for display on an imaging device isstored on RCD 60.

An RCD 60, of some embodiments, will be further configured to receive 84user input obtained through the user interface 32 of an imaging device30 and transferred to the RCD 60 over communications links 38 & 64. Oncethis input data is received at an RCD 60, the input data may beprocessed 86. This processing 86 may comprise conversion of the data toa new format, execution of commands contained within the data or someother process. Once the input data has been processed 86, the processedoutput may be sent 88 back to the imaging device 30 where the processedoutput may be used in an imaging device process or function.

In some embodiments, as described with reference to FIG. 9, an RCD 60may send 90 menu data configured for an imaging device display 36 usinga markup language. The markup language menu data is then received at theimaging device 30 and displayed to a user. Typically, this will promptthe user to enter an input on the imaging device user interface 32. Thisuser input will then be sent by the imaging device 30 to the RCD 60. TheRCD 60 will then receive 92 the input data prompted by the display ofthe menu data on the imaging device 30. Once received, the input datamay be processed 94 on the RCD 60. Processing may comprise theselection, recordation and/or modification of a form, document or otherdata stored on RCD 60, the authorization of a user identified by theuser input, the translation of a document input by the user, generationof a map or other directions related to user input or some other processor function.

Some embodiments of the present invention may be described withreference to FIGS. 10 & 11. These embodiments comprise at least one RCD60 and a plurality of imaging devices 30 a-30 d. In these embodiments,at least one of the imaging devices 30 a-30 d comprises a user interface32 with a display 36 and user input panel 34 that is integral with thedisplay (i.e., touch-screen) or a separate input unit. RCD 60 isconnected to imaging devices 30 a-30 d by a communications link andnetwork 100 to enable data transmission between RCD 60 and imagingdevices 30 a-30 d.

In these embodiments, menu data is stored on RCD 60 and sent 110 to atleast one of the imaging devices 30 a-30 d where the menu data isdisplayed on a user interface. Any of Imaging devices 30 a-30 d thatreceive the menu data are configured to accept 112 and transmit 114 userinput to an RCD 60. Once the user input data is received at the RCD, thedata may be processed 116 as discussed in previously describedembodiments. The result of processing 116 may then be sent 118 back toany combination of the imaging devices 30 a-30 d.

In these embodiments, a single RCD 60 may be used to provide processingpower, resources and functionality to a plurality of imaging devices 30a-30 d without reproducing these resources in each imaging device. Insome embodiments, data generated by input on one imaging device 30 a maybe directed to another imaging device 30 d for processed data output orfinal processing.

Event Notification Subscription Embodiments

Embodiments of the present invention provide systems and methods fornotification techniques between an imaging device (IDev) and anapplication, which may be local or on a remote computing device (RCD).These notification methods and systems may be used for error reportingand other purposes. Applications may receive these notifications bysubscribing to a notification application on an IDev. The IDev may thennotify an application when a specific event occurs on the IDev or anassociated device.

In some embodiments, subscribing to an event may comprise making a callto an IDev Web Service and identifying an event for which notificationis desired. In some embodiments, an application may, additionally,subscribe to an event within the context of a single job or globally(for all jobs). In some exemplary embodiments, an application may exposea web service of its own through which the IDev may send notifications.

In some embodiments, receiving an event notification may compriseimplementing a web service through which to receive event notifications.In some embodiments, a web service or another application may be used tosubscribe to an event notification process. A web service or anotherapplication may also be used to process event data when an event occurs.In some embodiments, an event method may be called any time an eventoccurs. An event method may also be job-specific wherein it only sends anotification message during a specific job. In some embodiments, an“eventdata” parameter may be used. The eventdata parameter may comprisea structure containing event specific data, such as a job identifier,user credentials, and/or other data.

In some exemplary embodiments, an application may subscribe to an errornotification process that is triggered by an error of some type in theIDev system. In some of these embodiments, this may be described as anON_SYSTEM_ERROR event. An error condition may be triggered by severalfactors. In some exemplary embodiments, an error condition may betriggered by an “out of paper” condition which has stopped a printprocess, or, in the case of a scan job, a “document not found” conditionin the input tray.

In some exemplary embodiments, which comprise a web service, an eventtrigger may comprise application-provided configuration data that issyntactically and semantically valid in terms of the Web ServiceDescription Language (WSDL) and overall rules, but is still not valid.For example, a user may configure a fax operation and specify a faxnumber which is not a valid phone number.

In some embodiments of the present invention, an application or devicethat wants information relating to IDev activity may request from theIDev a list of events for which the IDev is capable of sendingnotifications. These events may be related to native functions and/orapplications or may be related to remote applications, which are incommunication with the IDev. In some embodiments, a subscribingapplication may use a SOAP method GetServiceEventElements to obtain alist of event elements for which an IDev notification application iscapable of sending notifications. Once the list of availablenotification events is known, a subscribing application may request asubscription to an event on the list. An IDev notification applicationmay then record the notification request in a notification record andnotify the subscribing application if the event occurs.

Some embodiments of the present invention comprise processes that may beimplemented as Web Service methods. Some of these processes are referredto by specific names that are used in exemplary embodiments. These namesmay be related in a syntax using the name followed by a closed set ofparentheses (i.e., Event( ), CreateJob( ), Authenticate( )). Adescription of an exemplary embodiment comprising these methods andtheir functions and attributes is found in Appendix A.

In some embodiments of the present invention, a notification applicationmay be based on a subscription model, where local or networkapplications that wish to receive notifications may subscribe in advanceto events with a given IDev. In some embodiments, an IDev may implementa subscribers list and manage it. This may be done through a webservice. In these embodiments, event notifications may be messages thatmay be sent to subscribing applications when certain conditions takeplace on the IDev.

In some embodiments, a purpose of the event notification process may beto allow remote clients to receive information about events that takeplace on the IDev or an associated device during execution of a specificjob. In these embodiments, a job-specific subscription may be requestedfor which notification only occurs while the specific job is executing.In an exemplary embodiment of the present invention, an IDevnotification application may send a Hello( ) SOAP request to aregistered application of External Authority (subscribing application)each time a new application is registered with the IDev or each time anapplication is removed from the list on a given IDev, such as an MFP.

Embodiments may comprise events that an application has subscribed tobeing associated with a specific job ticket. These “per job ticket”subscriptions may remain valid for the lifespan of the job ticket. Whena particular job ticket instance expires, the subscription associatedwith it may also expire. This type of subscription may be used by astandard user application. By subscribing to an event on aper-job-ticket basis, the subscriber may be notified about the eventwithin the context of the client's job. Subscription to a per-job-ticketevent will expire when the job ticket expires. A per-job-ticketsubscription embodiment is a sub-set of the broader job-specificsubscription embodiments.

Some embodiments of the present invention may define a notificationmechanism to be used for notifying a subscribing application abouteligible events that take place on the IDev or an associated applicationor device. In some embodiments, a notification mechanism may bespecified by the subscribing application when a notification request ismade or at some time before the actual notification occurs.

Some embodiments of the present invention comprise access control inwhich a notification application requires credential authenticationprior to granting a notification subscription. In these embodiments, anotification request may comprise a user credential or may be followedup with a user credential to authenticate the user. The notificationapplication may process the credential or send it to a remoteauthentication application for processing. Only when the credential issuccessfully authenticated will the subscription request be granted. Insome embodiments, only certain types of subscription request may requireaccess control and credential authentication. For example, a globalsubscription request (for all jobs on an IDev) may requireauthentication while a job-specific subscription request may not requireauthentication.

In some exemplary embodiments of the present invention, an IDevnotification application may run under a secure access mode. In thismode a request from a subscribing application may contain a SOAP headercomprising a security element of type SECURITY_SOAPHEADER_TYPE. Thiselement may contain user or account credentials. In some exemplaryembodiments the request may comprise some or all of the following XML orSOAP elements:

<?xml version=“1.0” encoding=“utf-8”?> <S:Envelopexmlns:S=“http://www.w3.org/2001/12/soap-envelope”> <S:Header> <Security><Credentials> <account-id>adent</account-id> <metadata><password>42isgood</password> </metadata> </Credentials> </Security></S:Header> <S:Body> <EnableDevice generic=”1.0”xmlns=”urn:schemas-sc-jp:mfp:osa-1-1” > <acl> <mfp-featuresgroupId=“1234”> <user-info> <account-id>fprefect</account-id></user-info> <mfp-feature xsi:type=“MFP_FEATURE_SCAN_TYPE”allow-use=“on”/> <mfp-feature xsi:type=“MFP_FEATURE_COPY_TYPE”allow-use=“on”/> <mfp-feature xsi:type=“MFP_FEATURE_PRINT_TYPE”allow-use=“on”/> <mfp-feature xsi:type=“MFP_FEATURE_FAX_TYPE”allow-use=“on”/> <mfp-feature xsi:type=“MFP_FEATURE_DOCFILING_TYPE”allow-use=“on”/> <mfp-feature xsi:type=“MFP_FEATURE_CUSTOM_SETTINGS_TYPE” allow-use=“off”/> <mfp-featurexsi:type=“MFP_FEATURE_ADMIN_TYPE” allow-use=“off”/> </mfp-features></acl> </EnableDevice> </S:Body> </S:Envelope>In further exemplary embodiments, a response message may be sent backthat may comprise the following XML or SOAP elements:

<?xml version=“1.0” encoding=“utf-8”?> <S:Envelopexmlns:S=“http://www.w3.org/2001/12/soap-envelope”> <S:Body><EnableDeviceResponse generic=”1.0”xmlns=”urn:schemas-sc-jp:mfp:osa-1-1” /> <S:Body> </S:Envelope>

In some embodiments of the present invention, account credentials may beprovided which may contain information about the user and application,such as the user login name and password. User or application accountcredentials may be provided inside a SOAP header element. The accountcredentials may be provided inside a CreateJob( ) request or inside thePJL stream. The original caller account credentials may be submitted asone of the parameters in this request. Credentials may also be sent in aseparate message or message exchange.

In an exemplary embodiment of the present invention, a messagecontaining user account data information may comprise the following XMLelements:

<?xml version=“1.0” encoding=“utf-8”?> <S:Envelopexmlns:S=“http://www.w3.org/2001/12/soap-envelope”> <S:Header><wsse:Security xmlns:wsse=“http://schemas.xmlsoap.org/ws/2002/07/secext” S:mustUnderstand=“1”> <wsse:UsernameToken><wsse:Username>bschacht</wsse:Username><wsse:PasswordType=”PasswordText”>ILoveHorses</wsse:Password> </wsse:UsernameToken></wsse:Security> </S:Header> <S:Body> <m:CreateJob generic=”1.0”xmlns:m=”urn:schemas-sc-jp:mfp:osa-1-1”> </m:CreateJob> </S:Body></S:Envelope>

Some embodiments of the present invention may comprise an Access ControlList (ACL). The ACL may comprise information about the permissions ofeach IDev user, IDev resources, and/or remote applications. A remoteapplication, such as an External Authority (described below), maymaintain the ACL and may provide it to a plurality of IDevs on thenetwork. The External Authority or another application may return theACL in response to an Authenticate( ) request from the IDev, or as aparameter in an EnableDevice( ) request sent to the IDev. The ExternalAuthority may send the EnableDevice( ) request when it does not receivethe Authenticate( ) request from the IDev. If a user starts a job fromthe operation panel interface, the IDev may not send the Authenticate( )request. The ACL response message may contain instructions on IDevfeatures that should be enabled or disabled for the requested account.If the method returns successfully, but without the ACL element, the MFPmay interpret this to mean that the credentials are valid and may enableall features for the user. In case of an error, the MFP may return afault element to the requesting application.

In some exemplary embodiments, only the IDev and the External Authorityapplication may use this method. The IDev may implement the client sideof this method and take the credentials and JobId data types asparameters. The purpose of this request may be to allow the ExternalAuthority to authenticate the user credentials and allow or disallowaccess to IDev features. This method may be reserved for exclusive usebetween the IDev and the registered External Authority application. TheIDev may implement the client side of this method, while the applicationmay implement the server side.

In some embodiments, applications with administrator level credentialsor other qualifications may be allowed to subscribe to events on aglobal basis, e.g. without a need to provide a job ticket at time ofsubscription. This type of subscription may never expire. In theseembodiments, events may be fired when a particular condition takes placeon the IDev. This type of global subscription may be used byapplications such as an accounting application or an external authorityapplication that may subscribe once to certain types of events and mayreceive notification from the IDev when an actual condition takes placefor any job or job ticket executing on the IDev. In these embodiments,subscription to an event may never expire. In some exemplaryembodiments, the best time to subscribe to an event on a global basismay be at the time the application discovers an enabled IDev device onthe network.

In some embodiments of the present invention, an IDev may be configuredto operate under the supervision of an “External Authority” applicationthat may have been assigned an exclusive decision-making role. An“External Authority” application may monitor or control the processes onthe IDev. As such, it may provide system enable or disabledecision-making. When an IDev runs under the control of such anapplication, the IDev features may remain disabled until enabled by theExternal Authority. The enable signal may come from such an ExternalAuthority application when the user account credentials have beenpositively validated. This type of application may also provide accesscontrol features to the IDev and may enable or disable specific featuresof the IDev based on the credentials submitted. The IDev may beconfigured to run under the control of only one External Authorityapplication. If configured to operate with an External Authority, theIDev may only execute jobs submitted by that External Authorityapplication or that have been authorized by that External Authority.

In some embodiments of the present invention, an IDev may be configuredto operate either as an uncontrolled native IDev, that is, with no“external authority,” or to operate under the control of an “externalauthority.” When an IDev operates as an uncontrolled native machine, allof its features may be enabled by default. On the other hand, when anIDev is configured to operate under the control of an ExternalAuthority, all of the features may be disabled by default. The ExternalAuthority application may then enable specific IDev features based onthe user provided credentials.

In some exemplary embodiments, An IDev may provide a configuration pagefor registering an application that can be accessed only byadministrators. An administrator may configure the external authorityapplication to implement at a minimum the following methods of theMFPCoreWS interface: the server side of the Hello( ) method, the serverside of the Authenticate( ) method, the server side of the Authorize( )method, and the client side of the EnableDevice( ) method. Anadministrator may also configure the external authority application toimplement: the client side of the Subscribe( ) method, the server sideof the Event( ) method, and if the external authority application needsto control the operation panel, the client side of the ShowScreen1( )and ShowScreen2( ) requests.

In some exemplary embodiments of the present invention, remoteapplications may subscribe/unsubscribe to/from event notifications bysending a Subscribe SOAP request message to the IDev. The “action”parameter in this SOAP request defines the action. If the value of the“action” parameter evaluates to “true” then the meaning of this SOAPrequest is to subscribe to a particular event, otherwise it is anunsubscribe request. In some exemplary embodiments, a remote applicationmay subscribe to an event by sending a Subscribe( ) SOAP request withthe action field set to true. To un-subscribe from an eventnotification, a remote application may send the Subscribe( ) SOAPrequest again with the action field set to false.

In other embodiments of the present invention, applications, such as anaccounting service may subscribe to certain events of interest on aglobal basis, without specifying a job ticket. By doing so, the overallapplication interaction with the IDev service may be simplified.

In some embodiments of the present invention, the lifetime of asubscription entry may depend on several factors. The most basic case iswhen the subscription record is removed from the subscriber list via aspecific user request to un-subscribe, as shown earlier. If asubscription request to an event has been made on a per-job basis, thenthe subscription may expire automatically when the job object itselfceases to exist.

In an exemplary embodiment, a web service method, such as the MFPCoreWSframework, may remove any references in the subscriber's database when ajob has been cancelled. If a subscription request to an event has beenmade on a global basis, the subscription record may never expire. TheMFPCoreWS framework will not remove it from the subscriber's database.The only way to remove it from the list may be to specifically requestremoval of this record to the application that initially subscribed to agiven event. Records in the subscriber's database may not be persistent.In this case, when the device powers down all subscription records maybe lost and no notifications of that fact will be sent to the originalsubscribers.

In some embodiments of the present invention an IDev may send eventnotifications to subscribing applications. These event notifications maycomprise notifications triggered by events related to IDev functions,IDev applications and remote applications. Some exemplary eventscomprise job creation, the beginning of job execution, the end of jobexecution, job cancellation, job termination, job abortion, user login,user logout and many other events.

In some exemplary embodiments, the IDev may send a ON_JOB_CREATE eventnotification when a remote application successfully creates a new jobusing the CreateJob( ) method. The IDev may send a ON_JOB_EXECUTE eventwhen a remote application issues a ExecuteJob( ) request and the jobbegins executing successfully on the IDev. The IDev may send aON_JOB_CANCEL event when a remote application issues a CancelJob( )request. The IDev may send a ON_JOB_CLOSE event when a remoteapplication issues a CloseJob( ) request and the job begins executingsuccessfully on the IDev. The IDev may send a ON_JOB_ABORT event toregistered applications when the user terminates a job from the IDevoperation panel using the Job Status mode. The IDev may send anON_JOB_STARTED event to a subscribing application when an operationpanel initiated job begins executing on the IDev. The IDev may send anON_JOB_COMPLETED event when an IDev initiated job stops executing on theIDev for any reason, including successful completion of a job or anerror condition that caused the job to stop.

This ON_JOB_COMPLETED event may provides registered subscribers with thereason this job stopped, such as successful completion or an errorcondition. In addition, the ON_JOB_COMPLETED event may contain jobconfiguration information and the JobResults data structure to providethe IDev resource use details of this job. The IDev may send anON_USER_LOGOUT event to subscribing applications when a user logs outfrom the IDev at the operation panel. The sequence that the userexecutes to log out from the IDev may be specific to the IDev itself.The actual action that causes the user log-out event may be devicespecific, and as such, is of no concern to the monitoring application.In any case, when the monitoring application receives the ON_USER_LOGOUTevent it means that the currently logged-on user session with the IDevhas terminated. The IDev may generate this event type when the userexecutes the log-out sequence on the IDev operation panel or when thesession times out. This may be the IDev automatic logout when the userhas abandoned the machine.

In some embodiments, an IDev may send a notification when a specificIDev hardware key is pressed. The IDev may send an ON_HKEY_PRESSED eventnotification to subscribers when a hardware key is pressed. In someembodiments, this may occur when one of the keys of typeE_MFP_KEY_ID_TYPE has been pressed by the user on the IDev. This eventmay be triggered by pressing the KEY_COPY, KEY_IMGSND, KEY_PRINT,KEY_FAX, KEY_DOC_FILING, KEY_JOB_STATUS, KEY_CLEAR_ALL,KEY_SPECIAL_FUNCTIONS, KEY_CUSTOM_SETTINGS, or KEY_PROGRAM keys. TheIDev may send an ON_SYSTEM_READY event to subscribing applications whenan IDev system component becomes ready for operation. The IDev may alsosend an ON_SYSTEM_ERROR event to subscribing applications when aninternal system error occurs on the IDev such as a paper jam, the IDevis out of paper, and so on. The application may then acquire morespecific information about the problem by issuing a GetDeviceStatus( )request.

In other embodiments of the present invention, an event notification maycomprise some information when sent to a subscriber. The informationattached to the event notification may be provided by the MFPCoreWSframework inside an <event-data/> element. This element may have twoparts, of which one part may include a Header segment. In someembodiments, the information in this segment may not be event-typespecific and may be provided in all event types. In an exemplaryembodiment, this segment may contain the following information: accountinformation, which is represented via the <user-info/> element and thedevice information that is represented via the <device-info/> element.These elements may be represented in the following format: <user-info>,<account-id>bplewnia</account-id>, </user-info><device-infouuid=“SN0F21F359-AB84-36D110E6D2F9MNAR-650”>,<serial-number>0F21F359-AB84-36D110E6D2F9</serial-number>,<modelname>AR-650</modelname>, <location>DS EngineeringDept—Japan</location>, <mac_address>90:EF:0F:21:2A:36</mac_address>,<network_address>1.2.3.4</network_address> and </device-info>.

Some embodiments of the present invention may include elements with asecond event specific segment. In these embodiments the content of thissegment may be event type and job-type specific. The information in thissegment may be contained within the <details/> element.

In further embodiments of the present invention, the notificationmessage may be delivered to a subscribing application in more than oneway using a variety of mechanisms. In some embodiments, the followingtransport mechanisms for event message delivery may be used: SOAP, usinga notification method, such as the Event( ) method; E-MAIL, where thebody of the message will be the notification; HTTP-GET, HTTP_POST, usingthe HTTP POST mechanism to deliver the event data to subscribers; andRAW 2.0 protocol, a Sharp notification mechanism. An application maydesignate the event delivery mechanism at the time of subscription.

Some embodiments of the present invention may be described withreference to FIG. 12. In these embodiments, an imaging device (IDev) 120comprises a user interface 124, which is capable of receiving user inputand displaying data to a user. The user interface 124 will typicallycomprise a display, often in the form of a touch panel. The display maybe used to display data to a user. This data may comprise menu data toprompt for a user selection or data entry, such as a user ID andpassword, form selection or some other input. The imaging device 120 hasa communication link 122, which may comprise a typical computer networkconnection, a serial cable or some other wired or wireless communicationlink as described in other embodiments. The communication link 122 mayconnect the imaging device 120 to a remote computing device (RCD) 126 a,126 b, such as a server. The RCD 126 a, 126 b may be used to storedocuments, such as forms, and other data and make that data accessiblefrom the imaging device 120. The RCD 126 a, 126 b may also executeapplications that interact with or receive input from the imaging device120 and its user interface 124. In some embodiments, a database 125 maybe linked to the imaging device 120 and/or an RCD 126 a, 126 b. In someembodiments, an RCD 126 b or database 125 may be connected to an IDev120 over a wide area network such as the internet 128.

Some embodiments of the present invention may be described withreference to FIG. 13. These embodiments may comprise a subscribingapplication 130, such as an accounting application, which is capable ofrequesting and receiving a global or job-specific event notificationsubscription. A subscribing application may be an External AuthorityApplication, which has special privileges and access to restrictednotification resources. In some embodiments, the External AuthorityApplication may have access to global notifications that are notjob-specific. An External Authority Application may need to submitcredentials for authentication before receiving restrictednotifications.

Some embodiments may further comprise other remote subscribingapplications 132A & 132B which may request event notificationsubscriptions from an imaging device (IDev) 136 event notificationapplication 138. These applications 132A & 132B may only have access tounrestricted notifications. The external authority application, remoteapplications and IDev notification application may communicate with eachother through means of a network 134 using SOAP methods or othermethods. The external authority application and remote applications mayalso designate an event notification transport mechanism 139 which maybe used for sending and receiving event notifications and related data.Typical event notification transport mechanisms comprise HTTP Post,e-mail, SOAP messages and other mechanisms.

Some embodiments of the present invention may be described withreference to FIG. 14. In these embodiments, a subscribing applicationmay send 140 a subscription request to an IDev notification application.A subscription request may comprise a subscribing application addressand an event type. In some embodiments, a subscription request may alsocomprise user or application credentials and other data. The IDevnotification application may then receive 142 the subscription requestfrom the subscribing application and record 144 the subscribingapplication ID and event identification in a subscription record. TheIDev notification application may then configure itself 146 to notifythe subscribing application identified in the subscription request whenthe event identified in the subscription request occurs.

In further embodiments of the present invention, as illustrated in FIG.15A, a job-specific subscription may be implemented. In theseembodiments, a subscribing application may send 150 a subscriptionrequest comprising a subscribing application address, an event type anda job ID to an IDev notification application. The IDev notificationapplication may receive 151 the subscription request comprising thesubscribing application address, the event type and the job ID from thesubscribing application. The IDev notification application may thenrecord 152 the subscription request data in a subscription record. TheIDev notification application may then configure itself 153 to notifythe subscribing application at the subscribing application address whenthe event described by the event type occurs during execution of the jobidentified by the job ID. A job ID may comprise a job ticket.

In further embodiments of the present invention, as illustrated in FIG.15B, an alternative job-specific subscription may be implemented. Inthese embodiments, a subscribing application may send 154 a simplesubscription request to an IDev notification application. The IDevnotification application may receive 155 the simple subscription requestand request an event type from the subscribing application. Thesubscribing application may then send 156 an event type to thenotification application. Upon receiving the event type, thenotification application may request 157 a job ID from the subscribingapplication. The subscribing application may then supply 158 a job ID tothe notification application. Once the notification application has thesubscription request, the event type and the job ID, the notificationapplication may configure 159 to send a notification to the subscribingapplication when the event identified by the event type occurs duringthe execution of the job identified by the job ID.

Some embodiments of the present invention, illustrated in FIG. 16,comprise an event notification subscription using a specifiednotification delivery mechanism. In these embodiments, a subscribingapplication may send 160 a subscription request with a subscribingapplication address, an event type and a specified delivery mechanism toan IDev notification application. The IDev notification application mayreceive 162 the subscription request with the subscribing applicationaddress, event type and specified delivery mechanism from thesubscribing application. The IDev notification application may thenrecord 164 the subscription request data, comprising the specifieddelivery mechanism, in a subscription record. The IDev notificationapplication may then configure itself 166 to notify the subscribingapplication at the subscribing application address using the specifieddelivery mechanism when an event described by the event type occurs. Insimilar embodiments, the subscription request, subscribing applicationaddress and specified delivery mechanism may be exchanged throughmultiple messages.

Other embodiments of the present invention may be described withreference to FIG. 17. In these embodiments, a subscribing application,such as an accounting application, may discover 170 an enabled IDev onthe network. The subscribing application may then obtain 172, from theIDev, a list of reportable events that the IDev is capable ofidentifying for notification purposes. In some embodiments, asubscribing application may detect these reportable events by meansother than a list supplied by the IDev, such as by identifying an IDevand searching an external source for specific IDev data. Reportableevents may also be determined through detection of IDev capabilitiesdirectly through various protocols.

Once reportable events have been identified, a subscribing applicationmay send 174 a subscription request to the IDev notificationapplication. This subscription request or a related message may comprisea subscribing application address to which notifications may be sent.The subscription request or a related message may also comprise one ormore event types selected from the reportable events obtained from theIDev. A subscription request or a related message may also identify ajob ID to an IDev notification application. The IDev notificationapplication may receive 176 the subscription request and any relatedmessages comprising a subscribing application address, an event type andany job ID (for job-specific notification embodiments) from thesubscribing application. The IDev notification application may thenrecord 178 the subscription request and any related data in asubscription record. The IDev notification application may thenconfigure itself 179 to notify the subscribing application at thesubscribing application address when the event described by the eventtype occurs. In some job-specific notification embodiments, thisnotification would only occur when the event occurs during execution ofthe job identified by the job ID.

Some embodiments of the present invention comprise a notificationsubscription with access control. In these embodiments, a subscribingapplication may be required to submit credentials before being granted asubscription. In some embodiments, only certain subscriptions requirecredentials while others do not.

Some embodiments of the present invention may be described withreference to FIG. 18. In these embodiments, a subscribing applicationmay send 180 a subscription request comprising credentials to an IDevnotification application. The IDev notification application may thenreceive 182 the subscription request comprising the credentials. Oncethe credentials have been received, the notification application mayauthenticate 184 the credentials. The notification application may thendecide 185 whether to deny 186 the subscription request or grant 188 thesubscription. When the credentials authenticate successfully and theuser/account is authorized to receive the requested notification, thesubscription request may be granted 188.

Further embodiments of the present invention may be described withreference to FIG. 19. In these embodiments, a subscribing applicationmay request 190 a notification subscription from a notificationapplication. The notification application may then receive 191 therequest and may, when the notification requested is restricted, request192 credentials from the subscribing application, if none were suppliedin the subscription request. The subscribing application may then send193 the credentials to the notification application which may thenreceive 194 the credentials. The notification application may thenauthenticate 195 the credentials and verify that the authenticateduser/account is authorized to receive the requested notification. Basedon this verification, the notification application may then decide 196whether to deny 197 the subscription or grant 198 the subscription.

Other embodiments of the present invention may be described withreference to FIG. 20. In these embodiments, a subscribing applicationmay send 200 a subscription request containing a credential to an IDevnotification application. The IDev notification application may thenreceive 201 the subscription request containing the credential and send202 the credential to an authentication application which may thenauthenticate 203 the credential. The authentication application may thennotify the notification application of the results of the authenticationprocess. The notification application may then deny the subscription204, when authentication is unsuccessful. When authentication issuccessful, the authentication application may send 206 anauthentication message to the notification application, which may thengrant 208 the subscription request.

Other embodiments of the present invention may be described withreference to FIG. 21. In these embodiments, a subscribing applicationmay send 210 a subscription request to an IDev notification application.The IDev notification application may then request 211 credentials fromthe subscribing application, which may then send 212 the credentials tothe notification application. The notification application may then send213 the credentials to an authentication application which mayauthenticate 214 the credentials. The authentication application maythen inform 215 the notification application of the results of theauthentication. Based on these results, the notification application maydeny the subscription 218 or grant 217 the subscription.

Further embodiments of the present invention may be described withreference to FIG. 22. In these embodiments, a subscribing applicationmay send 220 a subscription request comprising credentials to an IDevnotification application. The IDev notification application may thenreceive 221 the subscription request and the credentials and maydetermine 222 whether the subscription request is of a type thatrequires authenticated credentials. In some exemplary embodiments thesetypes of subscription requests may comprise a request for a globalsubscription from an external authority application such as anaccounting application or a subscription request for a protected job. Ifthe subscription request is restricted and does require authenticatedcredentials, the notification application may then authenticate 224 thecredentials. The notification application may then deny the subscriptionrequest 229 if the authentication is unsuccessful or if theauthenticated user/account is not authorized to receive the requestednotification. If authentication is successful and the user/account isauthorized to receive the requested notification, the subscriptionrequest may be granted 228. If the subscription request is notrestricted and does not require credentials 222, the subscriptionrequest may be granted 228 without processing the credentials.

Other embodiments of the present invention may be described withreference to FIG. 23. In these embodiments, a subscribing applicationmay send 230 a subscription request comprising credentials to an IDevnotification application. The IDev notification application may thendetermine 232 whether the subscription request is of a type thatrequires authenticated credentials. If the subscription request doesrequire authenticated credentials the notification application may thensend 233 the credentials to an authentication application which mayauthenticate 234 the credentials. The notification application may thenanalyze the results of the authentication process and deny thesubscription request 237 if the authentication is unsuccessful or if theauthenticated user/account is not authorized to receive the requestednotification. The notification application may also grant 236 thesubscription request if the authentication is successful and theauthenticated user/account is authorized to receive the requestednotification. If the subscription request is not restricted and does notrequire credentials 232, the subscription request may be granted 236without processing the credentials.

Further embodiments of the present invention may be described withreference to FIG. 24. In these embodiments, a subscribing applicationmay send 240 a subscription request to an IDev notification application.The IDev notification application may then receive 241 the subscriptionrequest and may then determine 242 whether the subscription request isof a type that requires authenticated credentials. If the subscriptionrequest does require authenticated credentials, the notificationapplication may then request 243 the credentials from the subscribingapplication. The subscribing application may then send 244 thecredentials to the notification application which may then receive 245the credentials. The notification application may then authenticate 246the credentials. The notification application may then analyze theresults of the authentication process and deny the subscription request249 if the authentication is unsuccessful or if the authenticateduser/account is not authorized to receive the requested notification.The notification application may also grant 248 the subscription requestif the authentication is successful and the authenticated user/accountis authorized to receive the requested notification. If the subscriptionrequest is not restricted and does not require credentials 242, thesubscription request may be granted 248 without processing thecredentials.

Other embodiments of the present invention may be described withreference to FIG. 25. In these embodiments, a subscribing applicationmay send 250 a subscription request to an IDev notification application.The IDev notification application may then receive 251 the subscriptionrequest and determine 252 whether the subscription request is of a typethat requires authenticated credentials. If the subscription requestdoes require authenticated credentials the notification application maythen request 253 the credentials from the subscribing application. Afterreceiving 254 the credentials from the subscribing application thenotification application may then send 255 the credentials to anauthentication application. The authentication application may thenauthenticate 256 the credentials and send the results to thenotification application. The notification application may then analyzethe results of the authentication process and deny the subscriptionrequest 259 if the authentication is unsuccessful or if theauthenticated user/account is not authorized to receive the requestednotification. The notification application may also grant 258 thesubscription request if the authentication is successful and theauthenticated user/account is authorized to receive the requestednotification. If the subscription request is not restricted and does notrequire credentials 252, the subscription request may be granted 258without processing the credentials.

Further embodiments of the present invention comprise systems andmethods for event notification. Some of these embodiments compriseglobal and job-specific notification. Some embodiments also comprisenotification by a specified delivery mechanism.

Some embodiments of the present invention may be described withreference to FIG. 26. In these embodiments, an IDev notificationapplication may detect 260 when a specific event occurs. The IDevnotification application may then check 262 to determine if the event isrecorded on a subscription record. The IDev notification application maythen chose not to send a notification 266 if the specific event is noton the subscription record. Alternatively, the notification applicationmay send 268 a notification of the specific event to any subscribingapplication when the event is found on the subscription record. Thesubscribing application may then receive 269 the notification of theevent from the notification application.

Other embodiments of the present invention may be described withreference to FIG. 27. In these embodiments, an IDev notificationapplication may detect 270 when a specific event occurs. The IDevnotification application may then check 271 to determine if the event isrecorded on a subscription record. The IDev notification application maythen choose not to send a notification 273 if the specific event is noton the subscription record. Alternatively, if the specific event is onthe subscription record, the notification application may then check 274if the subscription is for a global subscription or a job specificsubscription. If the subscription is a global subscription, thenotification application may send 279 a notification of the event to thesubscribing application.

If the subscription is job-specific, the notification application maycheck 276 to determine if the job was in progress at the time of theevent. If the job was not in progress at the time of the event thenotification application may choose not to send 278 a notification ofthe event as the job-specific subscription is not active. If the job wasin progress at the time of the event, the notification application maysend 279 a notification of the event to the subscribing application. Thesubscribing application may then receive 280 the notification of theevent from the notification application. A notification application maydetermine whether a job is in progress using a job ticket method,wherein job tickets are maintained by an application during theexecution of a job. Once a job has been completed, the job ticket may bedeleted.

Further embodiments of the present invention may be described withreference to FIG. 28. In these embodiments, an IDev notificationapplication may detect 290 when a specific event occurs. The IDevnotification application may then check 291 to determine if the event isrecorded on a subscription record. The IDev notification application maythen choose not to send a notification 293 if the specific event is noton the subscription record. If the specific event is on the subscriptionrecord, the notification application may then check 294 if the deliverymechanism for the notification has been designated by the user. If thedelivery mechanism for the notification has been designated by the user,the notification application may send 297 notification of the event tothe subscribing application using the designated delivery mechanism. Ifthe delivery mechanism for the notification is not designated by theuser, the notification application may send notification of the eventusing a default delivery mechanism 296. The subscribing application maythen receive 298 the notification of the event from the notificationapplication via the default or designated delivery mechanism when anotification message is sent.

Further embodiments of the present invention may be described withreference to FIG. 29. In these embodiments, an IDev notificationapplication may detect 300 when a specific event occurs. The IDevnotification application may then check 301 to determine if the event isrecorded on a subscription record. The IDev notification application maythen choose not to send a notification 303 if the specific event is noton the subscription record. If the specific event is on the subscriptionrecord, the notification application may check 304 whether thesubscription is global or job-specific.

If the subscription is global, the notification application may thencheck 309 if the delivery mechanism for the notification has beendesignated. If the subscription is job-specific, the notificationapplication may check whether the job was in progress 307 at the time ofthe event. If the job was not in progress when the event occurred, thenotification application may chose not to send a notice 308. If the jobwas in progress at the time of the event, the notification applicationmay check 309 if the delivery mechanism for the notification has beendesignated. If the delivery mechanism for the notification has beendesignated, the notification application may send 312 notification ofthe event to the subscribing application using the designated deliverymechanism. If the delivery mechanism has not been designated, thenotification application may send notification of the event using adefault delivery mechanism 311. The subscribing application may thenreceive 313 the notification of the event from the notificationapplication via the designated delivery mechanism or the defaultdelivery mechanism when a notification is sent.

Core Web Service Framework

Some embodiments of the present invention may be described withreference to FIG. 30. The embodiments comprise a core web serviceframework (CWSF) 350. CWSF 350 may comprise a platform for building,deploying and running a web service on an IDev, such as an MFP. Some mayprovide a standards-based, multi-language execution environment forbuilding distributed network applications. These applications maycontrol processes executing on the IDev.

In some embodiments, a CWSF 350 may comprise a hardware interface (HWIF)326 connecting to IDev hardware 320. An HWIF 326 may shield the CWSF 350from particular platform hardware specific details. A standardized HWIF326 may allow the CWSF 350 to communicate with multiple IDev hardwaredevices 320 meeting the interface standard.

An HWIF module 326 may provide hardware abstraction of an IDev thathosts a CWSF 350. An HWIF module 326 may comprise a set ofdevice-independent APIs that the CWSF 350 uses to communicate withactual IDev hardware 320 components. On the other side, an HWIF module326 may implement device specific operation that it uses to control thehardware components of a particular platform. In this way, the HWIF 326may shield the CWSF 350 from actual hardware architecture details.

An HWIF module 326 may also serve as a source of notifications that theCWSF 350 receives through a through a status monitoring module (SMM)330. These notifications may be passed to the CWSF 350 via the SMM 330by means of callback calls. For example, and not by way of limitation,an HWIF module 326 may act as a source of a Started NotificationCallback, which is posted when a device is about to start executing ajob. An HWIF 326 may also be the source of a Completed NotificationCallback, which may be posted when a job is completed. An HWIF 326 mayalso be the source of a State Change Notification Callback, which may beposted when a job changes its state. An HWIF 326 may also be the sourceof a Page Notification Callback, which may be posted when a page is readin or printed.

In some embodiments, a CWSF 350 may comprise a System Architecture Layer(SAL) 324 that is responsible for translating high-level applicationrequests into a sequence of requests specific to a job type at the HWIF326 level, thereby hiding the complexity from the application. The SAL324 may group together a sequence of atomic operations into high-levelfunctions. A SAL 324 may provide a logical connection to an HWIF module326. A SAL 324 may also register a set of notification callbacks withthe HWIF module 326. When certain conditions occur while a job executes,the SAL 324 may receive corresponding notification from an HWIF module326. A SAL 324 may also be the source of event notifications. In someembodiments, a SAL 324 may perform an On_Job_Started notification and/oran On_Job_Completed notification.

The architecture of some embodiments of the present invention may bebased on the concept of a job. Depending on the actual devicecapabilities and device architecture, more than one job may be inprogress on an IDev at the same time. For example, and not by way oflimitation, a user may execute a scan job while another client issubmitting a print job. At the same time, another user may be receivinga fax message and an administrator may be performing an administrativejob on the device. In embodiments of the present invention, all thesejobs may execute at the same time because each job is identified by aunique identity that is represented by a job object.

The mechanism within the CWSF 350 that controls this dynamic jobenvironment may be referred to as a job queue manager (JQM) 328. A JQM328 may manage jobs processed by the system. These jobs may berepresented by job objects related to user processes executing on adevice. Each job may be represented by a job identifier (job ID) and beassociated with job settings, job results and an access control list(ACL). The ACL may comprise detailed information about access to jobinformation by notification subscribers. A JQM 328 may manage each jobobject for its entire lifetime. A JQM 328 may perform functions such asjob object creation, job object destruction, managing job settings,keeping track of security data associated with a job's user, keepingtrack of job state and status and other functions.

A JQM 328 may also be the source of an event notification. In someembodiments, a JQM 328 may be the source of an On_Job_Createnotification, and On_Job_Execute notification, an On_Job_Closenotification, an On_Job_Cancel notification and other notifications.

A JQM 328 may maintain a job object database 325 of jobs currently beingexecuted on an IDev or associated hardware or applications. The jobobject database 325 may also comprise an execution journal that persistsacross device power cycles even when other job information may be lost.

In some embodiments, a CWSF 350 may also comprise a status monitoringmodule (SMM) 330. The SSM may monitor the status of a device or a jobexecuting on a device. An SMM 330 may monitor changes in device and jobstates. An SMM 330 may also register a set of notification callbackswith a HWIF module 326. An SMM 330 may inform the JQM 328 or an NM 332about job or device state changes or other notifications. An SMM 330 maybe the source of an On_System_Error notification.

In some embodiments, a CWSF 350 may comprise a notification module (NM)332. An NM 332 may receive event notifications from many differentsources within the CWSF 350. An NM 332 may receive signals indicatinginternal IDev events or receive other notifications of events occurringon IDev hardware 320, on CWSF 350 modules, on remote applications 346 orother events. When a notification is received, an NM may communicatewith a JQM 328 to create an event data message. An NM 332 may alsocontact a subscriber manager (SM) 338 to find out whether there are anysubscribers interested in receiving notification of an event. If atleast one subscriber is found, the NM 332 may attempt to deliver eventnotification data to that subscriber. If a subscriber has identified aspecific notification method, the NM 332 may attempt to deliver thenotification using a transport protocol designated by the subscriberduring a subscription request or at some other time.

Some embodiments of a CWSF 350 may also comprise a user interface (UI)processor 334. A UI processor 334 may interface with an IDev UI panel322. A UI processor 334 may provide UI content to IDev panel 322 toprompt for user input or inform a user of a condition on the IDev, aCWSF module or a remote application. A UI processor 334 may also acceptuser input from an IDev panel 322 and relay that input to IDev hardware320, a CWSF module or a remote application 346. A UI processor 334 mayenable remote applications 346 to display application-specific screensusing an industry standard markup language, such as XHTML, to defineforms. A UI processor may also be the source of event notifications suchas an On_Hkey_Pressed notification, an On_User_Logout notification oranother notification.

A CWSF 350 may also comprise a web service module (WSM) 336. A WSM 336may provide a Simple Object Access Protocol (SOAP) interface for anIDev. Remote applications 346 may use a WSM 336 through a set of SOAPinterface methods to control IDev hardware 320 including an IDev UIpanel 322. A remote application 346 may also access and/or report toCWSF 350 modules through the WSM 336.

In some embodiments, a CWSF 350 may comprise a subscriber manager module(SMM) 338. An SMM 338 may manage a subscriber database 335 in whichsubscriber data is maintained for event subscriptions.

Some embodiments of a CWSF 350 may also comprise a markup languagelibrary, such as an XML library 340. XML library 340 may comprise autility code library. XML library 340 may provide function for managingXML content. These functions may be used for parsing and/or generatingXML data.

A CWSF 350 may also comprise an event delivery module (EDM) 324. An EDM342 may deliver even notification messages to subscribers. An EDM 324may access subscriber preferences, which may be stored in subscriberdatabase 335 in some embodiments. This subscriber data may be used toselect a transport mechanism for notification delivery.

Some embodiments of the present invention are illustrated in FIG. 31. Inthese exemplary embodiments, remote applications, such as a securityapplication 350, a “higher authority” application 352 or otherapplications 354 may connect to an IDev 364 over a communication link,such as a network 356. In these embodiments, an MFP Core Web Service(CWS) 365 may expose a SOAP interface to the external applications350-354. When a remote client application 350-354, makes a SOAP requestto the IDev, the CWS 365 assumes the responsibility of translating themarkup language (e.g., XML) data representation of the request into abinary form that can be processed by the device. The CWS 365 may alsotranslate any binary data returned to the remote clients into a suitablemarkup language.

In these exemplary embodiments, a CWS 365 may also assume theresponsibility of verifying and validating the input markup languagestream that is received from a remote client 350-354. This datavalidation may be performed according to the rules expressed in a WebService Definition Language (WSDL) definition document for the SOAPinterface. While a CWS 365 is processing a client SOAP request, it mayalso return error information serialized as a SOAP fault message.

When executing in secure mode, a CWS 365 may assume the responsibilityof assuring that a request comes from an authorized source and that theuser making the request has sufficient rights to make the request. A CWS365 may also perform user session management.

The terms and expressions which have been employed in the forgoingspecification are used therein as terms of description and not oflimitation, and there is no intention in the use of such terms andexpressions of excluding equivalence of the features shown and describedor portions thereof, it being recognized that the scope of the inventionis defined and limited only by the claims which follow.

1. An apparatus for imaging device (IDev) event notification using acore web service framework (CWSF), said apparatus comprising: a) astatus monitoring module (SMM) for monitoring changes in device and jobstates and for acting as a source for an event notification; b) asubscriber manager (SM) for receiving subscription requests from a webservice module (WSM) and for communicating with a notification module(NM); c) wherein said notification module (NM) receives eventnotifications from said sources for event notification and other sourcesand communicates with a job queue manager (JQM) to create an event datamessage and wherein said NM communicates with said SM to determine whichsubscribers are to receive notifications; d) wherein said WSM provides asimple object access protocol (SOAP) interface with remote applications,wherein said remote applications controls IDev hardware by sending aSOAP request that is translated to IDev device language by said WSM andforwarded to elements within said IDev, wherein said WSM receives asubscription request from a remote application as a SOAP request andtranslate and forward said subscription request to said SM, and whereinsaid WSM receives an event notification from said SM when an eventdescribed in said subscription request occurs, and said WSM sends localnotification menu content, formatted as a markup language message, to aUI processor in response to said receipt of an event notification; e) amarkup language library comprising a utility code library, wherein saidmarkup language library is employed in parsing and generating markuplanguage data; f) a system abstraction layer (SAL) for grouping togethera sequence of atomic operations into high-level functions; and g)wherein said UI processor creates IDev front panel menu content inresponse to receiving said local notification menu content, wherein saidIDev front panel menu content is formatted as a front panel markuplanguage message and wherein said UI processor sends said front panelmenu content to an IDev front panel user interface.
 2. An apparatus asdescribed in claim 1 wherein a notification is passed to said CWSF viasaid SMM by means of a callback call.
 3. An apparatus as described inclaim 1 wherein said JQM maintains a job object database of jobscurrently being executed on said IDev and on associated hardware andapplications.
 4. An apparatus as described in claim 1 wherein said JQMcomprises an execution journal that persists across IDev power cycles.5. An apparatus as described in claim 1 wherein said NM may receivesignals from remote applications indicating the occurrence of events atthose remote applications.
 6. An apparatus as described in claim 1wherein said WSM further performs data validation using a web servicedefinition language (WSDL) definition document for the SOAP interface.7. An apparatus as described in claim 1 wherein said WSM further assuresthat a request comes from an authorized source with sufficient rights tomake said request.
 8. A method for imaging device (IDev) eventnotification using a core web service framework (CWSF), said methodcomprising: a) receiving a subscription request via a Web Service Module(WSM); b) parsing said subscription request using a markup languagelibrary comprising a utility code library; c) sending said parsedsubscription request to a subscriber manager (SM), which receivessubscription requests from remote applications via said Web ServiceModule (WSM) and wherein said SM communicates with a notification module(NM); d) determining whether a requester of said notification request iseligible to receive a notification, said determining being performed bya job queue manager (JQM), which manages IDev system jobs through theuse of job objects related to user processes and wherein said JQMmanages an access control list (ACL), which allows said JQM to restrictjob notification access to entities listed on said ACL; e) recording asubscription using said SM when said subscription requester is eligiblefor said subscription; f) monitoring said IDev with a status monitoringmodule (SMM), which monitors changes in device and job states; g)receiving an event notification, at said NM, from a component in saidIDev; h) creating an event data message with said NM in response toreceipt of said event notification; i) sending said event data messageto said requester; and j) receiving an event notification at said WSMfrom said SM; k) creating local notification menu content, formatted asa markup language message with said WSM; l) sending said localnotification menu content to a UI processor; m) creating IDev frontpanel menu content, at said UI processor, in response to receiving saidlocal notification menu content, wherein said IDev front panel menucontent is formatted as a front panel markup language message; n)sending said front panel menu content from said UI processor to an IDevfront panel user interface; and o) displaying said front panel menucontent at said front panel user interface; and p) grouping together asequence of atomic operations into high-level functions by a systemabstraction layer (SAL).
 9. A method as described in claim 8 wherein anotification is passed to said CWSF via said SMM by means of a callbackcall.
 10. A method as described in claim 8 wherein said JQM maintains ajob object database of jobs currently being executed on said IDev and onassociated hardware and applications.
 11. A method as described in claim8 wherein said JQM comprises an execution journal that persists acrossIDev power cycles.
 12. A method as described in claim 8 wherein said NMreceives signals from remote applications indicating the occurrence ofevents at those remote applications and create an event data message inresponse to said signals.
 13. A method as described in claim 8 whereinsaid WSM further performs data validation using a web service definitionlanguage (WSDL) definition document for the SOAP interface.
 14. A methodas described in claim 8 wherein said WSM further assures that a requestcomes from an authorized source with sufficient rights to make saidrequest.